Searching data using pre-prepared search data

ABSTRACT

Methods and devices for searching are described. In one aspect, the method includes: receiving a search query; identifying a search data file associated with a third party application, the search data file being prepared according to predetermined format rules by the third party application, and stored, prior to receiving the search query; searching, at least a portion of the search data file using the search query to identify information that matches the search query; using the predetermined format rules to identify associated information in the search data file, the associated information being related to the information that matches the search query; obtaining search results from at least one other source; and generating a display of search results based on both the information matching the search query and the associated information, the display including the search results from the at least one other source.

TECHNICAL FIELD

The present application relates to the searching and handling of data onan electronic device and, more particularly, to search methods anddevices.

BACKGROUND

Electronic devices are often equipped with one or more third partyapplications. Such third party applications may, for example, provideadded functionality to the electronic device. For example, such thirdparty applications may include web browsers, communication applicationssuch as instant messaging applications, mapping applications, or otherapplications.

Such applications may have data associated therewith. For example, webbrowsers may track a browsing history and/or bookmarks, mappingapplications may track a history of visited places, etc. Traditionally,such data could be accessed through the application itself. That is, theapplication could be launched and the data could then be accessed viathe application's user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made, by way of example, to the accompanyingdrawings which show example embodiments of the present application, andin which:

FIG. 1 is a block diagram illustrating an example electronic device inaccordance with example embodiments of the present disclosure;

FIG. 2 illustrates a block diagram of an example search data file inaccordance with example embodiments of the present disclosure;

FIG. 3 is a flowchart of an example method for searching data inaccordance with example embodiments of the present disclosure;

FIG. 4 is a flowchart of a further example method for searching data inaccordance with example embodiments of the present disclosure;

FIG. 5 is a block diagram illustrating another example electronic devicein accordance with example embodiments of the present disclosure;

FIG. 6 is a flowchart of a further example method for searching data inaccordance with example embodiments of the present disclosure; and

FIG. 7 is an example display screen in accordance with exampleembodiments of the present disclosure.

Like reference numerals are used in the drawings to denote like elementsand features.

DETAILED DESCRIPTION

In one example embodiment a processor-implemented method of searchingdata associated with an electronic device is described. The methodincludes: receiving a search query at a search application; identifying,by the search application, a search data file associated with a thirdparty application, the search data file being prepared according topredetermined format rules by the third party application, and stored,prior to receiving the search query, at a location of memory at whichthe search application is configured to scan for the search data file;searching, by the search application, at least a portion of the searchdata file using the search query to identify information that matchesthe search query; using the predetermined format rules to identifyassociated information in the search data file, the associatedinformation being related to the information that matches the searchquery; obtaining search results from at least one other source; andgenerating a display of search results based on both the informationmatching the search query and the associated information, the displayincluding the search results from the at least one other source.

In another example embodiment, an electronic device is described. Theelectronic device includes a memory storing a search data fileassociated with a third party application. The search data file isprepared according to predetermined format rules by the third partyapplication. The electronic device further includes a processor coupledwith the memory. The processor is associated with a search applicationwhich configures the processor to: receive a search query; identify thesearch data file associated with the third party application; search atleast a portion of the search data file using the search query toidentify information that matches the search query; use thepredetermined format rules to identify associated information in thesearch data file, the associated information being related to theinformation that matches the search query; obtain search results from atleast one other source; and generate a display of search results basedon both the information matching the search query and the associatedinformation, the display including the search results from the at leastone other source.

In some example embodiments, a further processor-implemented methodsearching data associated with an electronic device is described. Themethod includes: determining whether a first sandbox is locked; if thefirst sandbox is unlocked, obtaining search results from one or moreapplications associated with the first sandbox; obtaining search resultsfrom one or more applications associated with a second sandbox; anddisplaying the search results from the applications associated with thefirst sandbox together with the search results for the applicationsassociated with the second sandbox.

Other example embodiments of the present disclosure will be apparent tothose of ordinary skill in the art from a review of the followingdetailed description in conjunction with the drawings.

Example embodiments of the present disclosure are not limited to anyparticular operating system, electronic device architecture, serverarchitecture or computer programming language.

Example Electronic Device

Reference is first made to FIG. 1 which illustrates an exampleelectronic device 201. In the illustrated example embodiment, theelectronic device 201 is a communication device, such as a mobilecommunication device. In at least some example embodiments, theelectronic device 201 is a two-way communication device having data andvoice communication capabilities, and the capability to communicate withother computer systems, for example, via the Internet. Depending on thefunctionality provided by the electronic device 201, in various exampleembodiments the electronic device 201 may be a multiple-modecommunication device configured for data and voice communication, amobile telephone such as a smart phone, a tablet computer, an electronicbook reader, a wearable computer such as a watch, a PDA (personaldigital assistant), or a computer system.

A smartphone is a mobile phone which offers more advanced computingcapabilities than a basic non-smartphone cellular phone. For example, asmartphone may have an ability to run third party applications which arestored on the smartphone.

A tablet computer (which may also be referred to as a tablet) is anelectronic device 201 which is generally larger than a mobile phone(such as a smartphone) or personal digital assistant. Many mobile phonesor personal digital assistants are designed to be pocket sized. That is,mobile phones or personal digital assistants are generally small enoughto be carried by a person easily, often in a shirt or pant pocket whiletablet computers are larger and may not fit within pant pockets. Forexample, many tablet computers have a height which is seven inches (7″)or more.

In at least some example embodiments, the electronic device 201 is ahandheld electronic device. A handheld electronic device is anelectronic device 201 which is sufficiently small to be held in one ormore hands of a user. The term handheld electronic device includessmartphones and may also include tablet computers. In at least someexample embodiments, the handheld electronic device may be sufficientlysmall to be held in a single hand of a user. For example, the handheldelectronic device may be a palm-sized device which is sized to be heldin the palm of a user's hand. From the description which follows, itwill be appreciated that the techniques and methods described herein maybe used in electronic devices 201 having limited display capabilities.

In other example embodiments, the electronic device 201 may be of a typenot specifically listed above.

The electronic device 201 includes a housing (not shown) which housescomponents of the electronic device 201. The internal components of theelectronic device 201 are constructed on a printed circuit board (PCB).The electronic device 201 includes a controller including at least oneprocessor 240 (such as a microprocessor) which controls the overalloperation of the electronic device 201. The processor 240 interacts withdevice subsystems, such as a wireless communication subsystem 211 forexchanging radio frequency signals with a wireless network 101 toperform communication functions. The processor 240 interacts withadditional device subsystems including one or more input interfaces 206(such as a keyboard, one or more control buttons, a camera 253, one ormore microphones 258, and/or a touch-sensitive overlay associated with atouchscreen display, etc.), flash memory 244, random access memory (RAM)246, read only memory (ROM) 248, auxiliary input/output (I/O) subsystems257, a data port 259 (which may be a serial data port, such as aUniversal Serial Bus (USB) data port), one or more output interfaces 205(such as a display 204, one or more speakers 256, or other outputinterfaces), a short-range communication subsystem 262, and other devicesubsystems generally designated as 264. Some of the subsystems shown inFIG. 1 perform communication-related functions, whereas other subsystemsmay provide “resident” or on-device functions.

One or more of the input interfaces 206 may be configured for receivinguser input to allow a user to interact with the electronic device 201.Such input interfaces 206 may, for example, allow a user to interactwith a graphical user interface provided on the electronic device 201.Instructions, commands, or other forms of input may be received by theelectronic device 201 via the input interfaces. For example, the inputinterfaces 206 may allow a user to interact with one or more interfaceelements displayed on a graphical user interface of the display 204. Thegraphical user interface may, in some example embodiments, include adisplay 900 of the type described below with reference to FIG. 7.

The input interfaces 206 may take a variety of forms. For example, anyone or combination of the following input interfaces 206 may be includedon the electronic device 201 and used for receiving user input: atouchscreen display, a control button, a trackball, trackpad, or opticalinput device, a keyboard, a camera 253 (which may be used, for example,to detect gesture-based input), an orientation or acceleration sensorsuch as an accelerometer (which may be used, for example, to detectgesture-based input performed by moving the electronic device 201),and/or a microphone 258 (which may be used, for example, to detectvoice-based commands). It will be appreciated that the foregoing list ofinput interfaces 206 is not exhaustive and that other input interfaces206 may be used instead of or in addition to any of the interfaces 206described above.

As noted previously, the electronic device 201 may include atouch-sensitive display 204 which may be referred to as a touchscreen ora touchscreen display 204. The touchscreen display 204 may beconstructed using a touch-sensitive input surface connected to anelectronic controller. The touch-sensitive input surface overlays thetouchscreen display 204 and may be referred to as a touch-sensitiveoverlay. The touch-sensitive overlay and the electronic controllerprovide a touch-sensitive input interface 206 and the processor 240interacts with the touch-sensitive overlay via the electroniccontroller. That is, the touchscreen display 204 acts as both an inputinterface 206 and an output interface 205.

In some example embodiments, the electronic device 201 may communicatewith any one of a plurality of fixed transceiver base stations of thewireless network 101 within its geographic coverage area. The electronicdevice 201 may send and receive communication signals over the wirelessnetwork 101 after the required network registration or activationprocedures have been completed.

In some example embodiments, the auxiliary input/output (I/O) subsystems257 may include an external communication link or interface, forexample, an Ethernet connection. The electronic device 201 may includeother wireless communication interfaces for communicating with othertypes of wireless networks, for example, a wireless network such as anorthogonal frequency division multiplexed (OFDM) network.

In the example embodiment illustrated, the electronic device 201 alsoincludes a memory module 230 (which may be flash memory) and a memorymodule interface 232. The memory module 230 may be removable from theelectronic device 201. Network access may be associated with asubscriber or user of the electronic device 201 via the memory module230, which may be a Subscriber Identity Module (SIM) card for use in aGSM network or other type of memory module for use in the relevantwireless network. The memory module 230 may be inserted in or connectedto the memory module interface 232 of the electronic device 201.

The electronic device 201 may store data in an erasable persistentmemory, which in one example embodiment is the flash memory 244. Invarious example embodiments, the data may include service data havinginformation required by the electronic device 201 to establish andmaintain communication with the wireless network 101. The data mayinclude a search data file 225. The search data file 225 will bediscussed in greater detail below. The data may also include servicedata 228. Service data is data that is associated with a service 227 andwill be discussed in greater detail below during the discussion of theservice 227.

The data port 259 may be used for synchronization with a user's hostcomputer system (not shown). The data port 259 enables a user to setpreferences through an external device or software application andextends the capabilities of the electronic device 201 by providing forinformation or software downloads to the electronic device 201 otherthan through the wireless network 101. The alternate download path may,for example, be used to load an encryption key onto the electronicdevice 201 through a direct, reliable and trusted connection to therebyprovide secure device communication.

In some example embodiments, the electronic device 201 is provided witha service routing application programming interface (API) which providesan application with the ability to route traffic through a serial data(i.e., USB) or Bluetooth® (Bluetooth® is a registered trademark ofBluetooth SIG, Inc.) connection to the host computer system usingstandard connectivity protocols. When a user connects their electronicdevice 201 to the host computer system via a USB cable or Bluetooth®connection, traffic that was destined for the wireless network 101 isautomatically routed to the electronic device 201 using the USB cable orBluetooth® connection. Similarly, any traffic destined for the wirelessnetwork 101 is automatically sent over the USB cable Bluetooth®connection to the host computer system for processing.

The electronic device 201 includes or is connectable to a power source.In the example embodiment illustrated, the power source is a battery238, such as a rechargeable battery that may be charged, for example,through charging circuitry coupled to a battery interface 236 such asthe serial data port 259. The battery 238 provides electrical power toat least some of the electrical circuitry in the electronic device 201,and the battery interface 236 provides a mechanical and electricalconnection for the battery 238. The battery interface 236 is coupled toa regulator (not shown) which provides power V+ to the circuitry of theelectronic device 201.

The short-range communication subsystem 262 is an additional optionalcomponent which provides for communication between the electronic device201 and different systems or devices, which need not necessarily besimilar devices. For example, the short-range communication subsystem262 may include an infrared device and associated circuits andcomponents, or a wireless bus protocol compliant communication mechanismsuch as a Bluetooth® communication module to provide for communicationwith similarly-enabled systems and devices.

A pre-determined set of applications that controls basic deviceoperations, including data and possibly voice communicationapplications, may be installed on the electronic device 201 during orafter manufacture. Additional applications and/or upgrades to anoperating system 222 or software applications may also be loaded ontothe electronic device 201 through the wireless network 101, theauxiliary I/O subsystem 257, the data port 259, the short-rangecommunication subsystem 262, or other suitable device subsystems 264.The downloaded programs or code modules may be permanently installed,for example, written into the program memory (i.e. the flash memory244), or written into and executed from the RAM 246 for execution by theprocessor 240 at runtime.

In some example embodiments, the electronic device 201 may provide twoprincipal modes of communication: a data communication mode and a voicecommunication mode. In the data communication mode, a received datasignal such as a text message, an email message, or a web page downloadwill be processed by the communication subsystem 211 and input to theprocessor 240 for further processing. For example, a downloaded web pagemay be further processed by a browser application or an email messagemay be processed by the email messaging application and output to thetouchscreen display 204. A user of the electronic device 201 may alsocompose data items, such as email messages, for example, using the inputinterfaces 206, such as the touchscreen display 204. These composeditems may be transmitted through the communication subsystem 211 overthe wireless network 101.

In the voice communication mode, the electronic device 201 providestelephony functions and operates as a typical cellular phone. Theoverall operation is similar to the data communication mode, except thatthe received signals would be output to the speaker 256 and signals fortransmission would be generated by a transducer such as the microphone258. The telephony functions are provided by a combination ofsoftware/firmware (i.e., a voice communication module) and hardware(i.e., the microphone 258, the speaker 256 and input interfaces).Alternative voice or audio I/O subsystems, such as a voice messagerecording subsystem, may also be implemented on the electronic device201. Although voice or audio signal output is typically accomplishedprimarily through the speaker 256, the touchscreen display 204 may alsobe used to provide an indication of the identity of a calling party,duration of a voice call, or other voice call related information.

The processor 240 operates under stored program control and executessoftware modules stored in memory such as persistent memory, forexample, in the flash memory 244. As illustrated in FIG. 1, the softwaremodules include operating system software 222 and software applications,such as a search application 221 and a third party application 226.

The search application 221 is configured to receive a search query froma user and, in response, to perform a search of data associated with theelectronic device 201. More particularly, the search application 221 maybe configured to receive one or more characters (which may bealphanumeric characters or symbols commonly associated with a keyboard,such as a QWERTY keyboard) representing a search query and to use thosecharacters as part of a search. That is, the search applicationdetermines whether data on memory of the electronic device 201 matchesthe search query (e.g. the input characters).

In some example embodiments, the search application 221 may provideas-you-type search results. That is, the search application 221 may beconfigured to perform a search following each character input and/orwhen there is a brief pause in the input of characters. That is, in atleast some example embodiments, a carriage return or other input (suchas clicking on a button labeled search, or an equivalent button) is notrequired in order to input a search query; the input of an additionalcharacter or a pause in the input of characters is treated as aninstruction to perform a search and a search is performed based on theinputted characters (even if the input is not yet complete).

The search application 221 is universal in that it is configured tosearch data associated with multiple sources. For example, the searchapplication 221 may search data associated with the operating system222, data associated with a third party application 226 (i.e. bysearching a search data file 225 associated with that application), dataassociated with a service 227 (i.e. service data 228), and/or other datasuch as data associated with other applications or services.

As will be described in greater detail below (e.g. with reference toFIG. 7), the search application 221 may be configured to generate adisplay (e.g. on the display 204) which includes search results from aplurality of sources. For example, search results from a third partyapplication 226 may be displayed together with search results from otherapplications or services 227.

Accordingly, the search application 221 may search within data that isowned by a third party application 226. The third party applications 226that may be searched by the search application 221 may include any oneof a number of various application types including, for example, a webbrowser, a mapping application, a communication application (such as anemail application, an instant messaging application, etc.), a socialmedia application (such as an application for interacting with a socialnetwork, such as Facebook™, Linkedin™, etc.). The third partyapplication 226 may be of another type in other example embodiments.

The third party application 226 may be any application apart from theoperating system 222 and apart from the search application 221. The term“third party” is meant to indicate that the application is separate anddistinct from the search application 221 and, in at least some exampleembodiments, separate and distinct from the operating system 222. Thatis, the search application 221 is not provided within the operatingsystem itself and is an application that may be added to the electronicdevice 201 after installation of the operating system and removed fromthe electronic device 201 without removing either the operating systemor the search application 221. The third party application may beprovided by a developer apart from the developer of the operating systemand/or the search application 221. However, in some example embodiments,the third party application 226 may be produced by the developer of thesearch application and/or the operating system 222. The third partyapplication may be referred to as a value-added application in someexample embodiments.

The third party application 226 may have its own data that is accessedby the third party application but which, in at least some exampleembodiments, is not shared with other applications. That is, the thirdparty application 226 has access to the data but other third partyapplications (or services 227) do not have access to that data. In orderto allow the search application 221 to include this data in the search,the third party application 226 specially prepares a search data file225. This file is prepared in advance of a search being performed (i.e.it is prepared before the search query is received) and is retrieved bythe search application 221 in order to provide search results associatedwith the third party application 226. The search data file 225 isprepared using predetermined format rules that are known to the searchapplication 221. That is, the search application 221 is able to read andinterpret the search data file 225.

The predetermined format rules may allow the third party application 226to designate at least some of the data within the search data file 225as searchable and some data within the search data file 225 as notsearchable. The search application searches only within the searchableportion of the file and excludes the non-searchable portion from thesearch. As will be described in greater detail below, in at least someexample embodiments, the non-searchable portion includes metadata thatmay be used by the search application 221 when rendering, groupingand/or sorting search results. For example, the metadata may define theorder by which search results will be presented. That is, the searchapplication 221 may consult the metadata to determine how to order thesearch results.

The operating system 222 may be configured such that the search datafile 225 may be a protected file. More particularly, at least someapplications on the electronic device 201 may be denied certain accessprivileges for the search data file 225. In at least some exampleembodiments, the third party application 226 which owns the file (i.e.the third party application which creates the search data file 225and/or inserts data into the search data file 225), is granted both readand write privileges to the search data file 225. That is, the thirdparty application 226 is permitted to both read data from the file andwrite data to the file. The search application 221 may be permitted (bythe operating system 222) to read from the search data file 225, but maybe prohibited from writing to the search data file 225. That is, thesearch application 221 has read-only access to the search data file 225.

In contrast, other applications (i.e. apart from the third partyapplication 226 and the search application 221) may not be permitted toread or write to the search data file 225. For example, another thirdparty application may be prevented from reading from the search datafile 225 and/or writing to the search data file 225. In some exampleembodiments, only the third party application 226 that owns the searchdata file 225 (i.e. the third party application 226 which generates thedata for the file) and the search application 221 are permitted to readfrom the file; other applications may be prohibited from reading fromthe search data file 225.

Thus, the search data file 225 may be specially configured so that thesearch application 221 is permitted to read the contents of the file inorder to provide search results but other applications (apart from thethird party application 226 that stores data in the search data file225) are prohibited from snooping within the file (i.e. they cannot readthe contents of the file because the operating system 222 does not grantthem read privileges).

Accordingly, each search data file 225 is associated with a particularapplication and provides search results for that application. The datawithin the search data file 225 is pre-configured. That is, the data isstored within the file before the search query is received (i.e. thefile is not generated in response to receiving a search query—if thethird party application 226 has data that it wishes to share with thesearch application, the file is preconfigured before the search query isreceived).

While the search data file 225 is illustrated as being a single file, insome example embodiments, the contents of the search data file 225 maybe split into multiple files. For example, a first file may storesearchable data and a second file may store non-searchable data, such asmetadata (i.e. data that is not searchable but that relates to thesearchable data).

Accordingly, the search data file 225 is prepared by the third partyapplication. The search data file 225 may, in at least some exampleembodiments, be stored in a storage area (such as a folder) associatedwith the third party application 226 (i.e. the application which storesdata in the search data file 225). In at least some example embodiments,the access privileges discussed above may be enforced with respect tothe storage area. That is, the operating system 222 may be configuredsuch that only the third party application 226 is permitted to write toany files stored within that storage area (e.g. within that folder), andthe third party application 226 and the search application 221 arepermitted to read from files stored within that storage area, whileother applications are not permitted to read or write to files stored inthat storage area.

While a single third party application 226 is illustrated in FIG. 1, inpractice the memory may contain a plurality of third party applications.A number of those third party applications may generate their own searchdata files 225, all prepared in a common format. That is, a plurality ofthird party applications may all abide by the same predeterminedformatting rules that are known to the search application 221. Byutilizing these formatting rules, the third party applications cangenerate data for a search using any data associated with thoseapplications that a user may wish to search and may then allow such datato be searched via the search application 221. That is, by storing thedata in the search data file 225 using the predetermined format rules,the search application 221 may then use its own knowledge of thepredetermined format rules to search relevant parts of the search datafile 225 to generate search results.

In at least some example embodiments, one or more services 227 may alsobe provided in memory of the electronic device 201. Like the third partyapplication 226, the service 227 is a software module that may be storedin memory of the electronic device 201. The service, however, differsfrom an application in that the service 227 is generally configured torun as a background process on the electronic device 201. Moreparticularly, applications typically require some user input (such asselecting an icon associated with the application from a home or startpage) in order to cause them to run on the electronic device 201. Whenthe application starts up, it is typically accompanied by an associatedgraphical user interface and the graphical user interface may remainactive while the application runs. In contrast, a service 227 may runwithout a graphical user interface and/or may not require user input inorder to run. The service 227 may be automatically initiated; forexample, when the electronic device 201 first boots up.

By way of example, in some example embodiments, email may be associatedwith an email service. The email service may, for example, run in thebackground and may monitor for emails sent to the electronic device 201and trigger a notification (such as an audible, visual or vibratoryalarm) upon receipt of an email.

At least some services may be associated with applications. For example,the email service (which monitors for emails and may trigger anotification upon receipt of an email) may be associated with an emailapplication (which may provide a graphical user interface for accessingemails, for example). Thus, the services and applications may becomplementary on the electronic device 201.

In at least some example embodiments, services 227 may also have dataassociated therewith. Such data may be referred to as service data 228.In some example embodiments, the service data 228 associated with aservice 227 may also be searched when a search query is received in thesearch application 221. However, in at least some example embodiments,the data associated with services may be searched in a different waythan the data associated with applications. As noted above, forapplications, search data may be pre-prepared (as a search data file225) for the search application 221 by the third party application 226and then searched by the search application upon receipt of a searchquery. This method allows the data of the application to be searchedwithout having to run the application. In contrast, since the service227 may already running, the search application 221 may provide thesearch query to the service 227 and may allow the service 227 to performthe searching of the service data 228 associated with that service 227.The service 227 may then return search results to the search application221 in a predetermined format. Then, the search application 221 mayrender the search results received from the service 227 together withthe search results obtained by searching the search data file 225.

In rendering the search results, the search application 221 may allowone or more of the search results to be invoked. For example, a searchresults may be activated to cause the third party application 226associated with that search result to be opened and the specific searchresult to be accessed from within the third party application 226. Forexample, if the search result is a record (such as an email, etc.), therecord may be opened when the search result is activated.

As will be discussed in greater detail below, in at least some exampleembodiments, the third party application 226 may be permitted to controlhow a search result is to be accessed when it is activated. Moreparticularly, a third party application 226 may pass a Uniform ResourceLocator (URI) to the search application 221 via the search data file225, which may be used to invoke a particular search result. In at leastsome example embodiments, if no URI is provided by the third partyapplication 226 and a search result is activated, then the third partyapplication associated with that search result may be invoked. Anapplication switch may be used when the third party application 226 isinvoked which directs the third party application 226 to open a specificrecord. For example, a record identifier associated with the searchresult which was activated may be used to inform the third partyapplication 226 of the record that is to be opened.

While the search application 221 may, in some example embodiments, belogically divided into multiple components. For example, in some exampleembodiments, the search application 221 may include both an applicationand a service (which may be referred to as a search service). Forexample, the application portion of the search application 221 mayprovide the graphical user interface features of the search application(e.g. it may allow a user to input a search query and may display searchresults). The application may interact with the service, which performsthe searching functions described herein. This structure may allow otherapplications to utilize the service associated with the searchapplication 221 to perform search queries. Thus, in at least someexample embodiments, features described herein as being performed by the“search application” may be performed by a search service. Thus, thesearch application may be a search service in some example embodiments.

Software modules associated with the electronic device 201 (such as thethird party application 226 and/or the service 227) or parts thereof maybe temporarily loaded into volatile memory such as the RAM 246. The RAM246 is used for storing runtime data variables and other types of dataor information. Although specific functions are described for varioustypes of memory, this is merely one example, and a different assignmentof functions to types of memory could also be used.

Example Search Data File

As noted in the discussion of FIG. 1 above, one or more applications(which may be referred to as third party applications 226) associatedwith the electronic device 201 may pre-prepare data which may be used bythe search application 221 for performing a search. More particularly,the data may be stored, by the third party application 226, as a searchdata file 225. The search data file 225 effectively acts as a databaseof possible search results for a specific application and may thereforebe referred to as a search results database and/or anapplication-specific search results database. An example search datafile 225 will now be described.

As noted above, the search data file 225 is prepared in a predeterminedformat by the third party application 226 associated with the datacontained in the search data file 225. That is, the search data file isprepared by a third party application 226 according to one or morepredetermined format rules. The format rules used by the third partyapplication 226 are known to the search application 221, thus allowingthe search application 221 to read and properly interpret the datacontained in the search data file 225.

The predetermined format rules allow for the creation of an associationbetween related data. For example, the predetermined format rules mayallow for the creation of records. Each record may be comprised ofrelated information. For example, a record may have a plurality offields and the fields may include data that is related.

In the example illustrated, the search data file includes data in atable. In the example, all of the data is illustrated using an Xcharacter, but it will be appreciated that the data will differ. Therows 140 a, 140 b, 140 c, 140 d of the table(s) are used to establishrecords. That is, all data in a given row is associated with a differentrecord. In the example illustrated, the columns 142 a, 142 b, 142 c, 142d, 144 a, 144 b, 144 c are used to denote different fields. That is,each column 142 a, 142 b, 142 c, 142 d, 144 a, 144 b, 144 c representsinformation of a specific type.

By way of example, if the search data file 225 was associated with a webbrowser application, each row may represent a separate browsing historyentry. By way of further example, a first column 142 a might represent auniform resource locator (URL), a second column 142 b might represent adate when the URL was last visited, a third column 142 c might representa page title associated with the URL, and a fourth column 142 d mightrepresent a time of day when the URL was last visited. The columns 144a, 144 b, 144 c of the non-searchable data table 132 may representmetadata related to the browsing history entries that may be used toallow the web browser application to control how the search application221 displays search results related to the web browser application.

It will be appreciated that the role of the rows and columns may bereversed in some example embodiments. That is, in some exampleembodiments, the rows 140 a, 140 b, 140 c, 140 d are used to indicatedifferent fields (i.e. data of different types) and the column 142 a,142 b, 142 c, 142 d, 144 a, 144 b, 144 c are used to establish records.For example, all data in a column may be associated with a commonrecord, but the differing rows may indicate differing types of data(i.e. different fields).

In the example illustrated, the search data file 225 includes twoseparate portions and, more particularly, two separate tables. A firstportion of the search data file 225 (which is referred to as asearchable data table 130 or a first table) is configured to besearchable and a second portion of the search data file 225 (which isreferred to as a non-searchable data table 132 or a second table) isconfigured such that it is not searchable. More particularly, the searchapplication 221 is configured to search the first portion of the searchdata file 225 but not the second portion of the file; the second portionof the file is excluded from the search.

In the example illustrated, the portion of the search data file 225 thatis searched is referred to as a searchable data table 130 and theportion that is not searched is referred to as a non-searchable datatable 132. While the search application 221 does not perform a search ofthe non-searchable data table 132 when a search query is received, thenon-searchable data table 132 is, nevertheless, used by the searchapplication 221. More particularly, the non-searchable data table 132includes metadata regarding the data in the searchable data table 130.This metadata is prepared by the third party application 226 and is usedby the search application to determine the manner by which searchresults obtained from the searchable data table 130 are to be displayed.More particularly, the metadata may be used for rendering, grouping orsorting of the search results.

Both portions of the search data file 225 (i.e. the searchable portionand the unsearchable portion) may be related to one another. Moreparticularly, data of the first table may be related with specificmetadata in the second table by row number or column number. Forexample, in some example embodiments, the data in the first row of thesearchable data table 130 is related with the data in the second row ofthe non-searchable data table 132. It will be appreciated that columnscould be used to establish this relationship in other exampleembodiments.

The metadata of the non-searchable data table 132 may take differentforms in different example embodiments. By way of example, in someexample embodiments, the metadata may specify an image path. The imagepath may be the path of an icon that is to be displayed when a searchquery matches a field of a particular record. By way of further example,in some example embodiments, an unbound uniform resource identifier(URI) may be specified in the metadata. The URI may be used to invoke agiven search result. That is, the URI may be used to open the searchresult in the third party application 226.

By way of further example, in at least some example embodiments, themetadata may be used to group or order search results. For example,metadata may assign records to one of a plurality of different groups.Multiple records may, in some example embodiments, be assigned to acommon group. This group information may be used by the searchapplication 221 when rendering search results. For example, in someexample embodiments, when multiple records of a common group includecontent that corresponds to the search query, those records may bedisplayed together in a common group. Alternatively, in some exampleembodiments, when multiple records of a common group include contentthat corresponds to the search query, only a single one of those recordsmay be displayed (e.g. the most current one of the records may bedisplayed, but older records of the same group may not be displayed).

Similarly, metadata may establish the relative priority of records. Whenthe search application 221 displays search results which identify aplurality of records, the search results may be displayed in an orderthat is determined by the metadata specifying the relative priorities.Thus, while the search application 221 may render the search results,the third party application 226 may control the manner by which thosesearch results are displayed.

Multiple third party application may be configured to generate searchdata files 225 according to the format defined above. The manner bywhich records are defined and fields are defined and the manner by whichsearchable data and non-searchable data are separated may be the samefor all such third party applications (i.e. all third party applicationsthat wish to be included in the search results for the searchapplication 221 may prepare a search data file 225 using these sameformat rules). That is, the search data files 225 generated by aplurality of these third party applications may follow the samepredetermined format rules, which are rules that are known to the searchapplication 221.

The predetermined format rules that are known to the search application221 may not specify the type of searchable data in the search data file225. That is, the search application 221, in at least some exampleembodiments, does not know the nature of any of the information in thesearchable data table 130; it simply knows the relationships betweendata in the table (i.e. whether two pieces of data are of a common typeor are related in the sense that they belong to a common record). By wayof further clarification, the first column in the searchable data table130 for one search data file 225 (associated with a first third partyapplication 226) may contain different data than is contained in thefirst column of the searchable data table 130 for another search datafile 225 (e.g. associated with a second third party application 226).The third party applications are permitted to include any data that theywould like to be searchable within the searchable data table 130(subject, perhaps, to some size constraints).

However, in at least some example embodiments, the non-searchable datatable 132 allows a limited number of pre-determined types of metadata tobe specified and, in at least some example embodiments, thepredetermined rules require that a particular type of metadata beprovided at a particular location of the non-searchable data table 132.For example, a particular column (or row, as the case may be) may beused, for all non-searchable data tables 132 in all search data files225 to specify metadata of a particular type. By way of example, in someexample embodiments a first column 144 a may be used to specify alocation of an image, a second column 144 b may specify a URI that maybe used to invoke a search result, and a third column 144 c may be usedto specify a relative priority of a record. Since the non-searchabledata is used to effectively pass commands to the search application(e.g. to allow the third party application to tell the searchapplication 221 how to group, sort and/or otherwise render searchresults for the third party application), the search application 221 maybe configured to treat data stored at a certain location (e.g. in aparticular column of the non-searchable data table 132) of thenon-searchable data table 130 as a particular type of data.

Accordingly, the predetermined rules discussed above are used by thethird party application 226 when creating the search data file 225 andare also used by the search application 221 when interpreting the searchdata files.

Search of Third Party Application Data

Referring now to FIG. 3, a flowchart of an example method 600 forproviding searching of data will now be discussed. The example method600 may be performed by the electronic device 201 of FIG. 1 (and/or bythe example electronic device 201 of FIG. 5). More particularly, theprocessor 240 of the electronic device 201 may be configured to performthe method 600. A memory associated with the processor 240 may includeprocessor-executable instructions which, when executed, cause theprocessor 240 to perform the method 600 of FIG. 3. In at least someexample embodiments, these processor-executable instructions areprovided in one or more of the software modules described above withreference to FIG. 1. For example, a third party application 226, asearch application 221 and/or an operating system 222 associated withthe electronic device 201 may configure the electronic device 201 toperform the method 600. Since a plurality of different softwarecomponents may cause the method 600 to be performed, the method 600 maybe comprised of a plurality of sub-methods each performed by a differentsoftware component.

For example, a portion 650 of the method 600 may be performed by theoperating system 222. That is, the operating system 222 may beconfigured to cause the processor 240 to perform a portion 650 of themethod 600. The portion 650 of the method 600 that is performed by theoperating system 222 may, itself, be considered a method.

Similarly, a portion 652 of the method 600 may be performed by the thirdparty application 226. That is, the third party application 226 may beconfigured to cause the processor 240 to perform a portion 652 of themethod 600. This portion 652 may also be considered a method.

Similarly, a portion 654 of the method 600 may be performed by thesearch application 221. That is, the search application 221 may beconfigured to cause the processor 240 to perform a portion 654 of themethod 600. This portion 654 may also be considered a method.

Thus, FIG. 3 describes a plurality of methods that may be performed. Amethod is described that may be provided by an operating system 222(i.e. the portion 650 of the method 600), a method is described that maybe provided by a third party application 226 (i.e. the portion 652 ofthe method 600), and a method is described that may be provided by asearch application 221 (i.e. the portion 654 of the method).Additionally, a method 600 may be jointly performed by the operatingsystem 222, the search application 221 and the third party application226, or by other software applications or modules.

At 602, the operating system 222 configures access rights for a searchdata file 225 (FIGS. 1 and 2) associated with the third partyapplication 226. The configuration performed at 602 may, in some exampleembodiments, be performed when the third party application 226 isinstalled on the electronic device 201. In other example embodiments,the configuration performed at 602 may be performed when an applicationis first run. That is, the first time an application is launched on theelectronic device 201, the configuration may be performed.

In at least some example embodiments, at 602, specific access rights areassigned to a file and/or folder. That is, access rights may beassigned, by the operating system 222 to the search data file 225 and/orto the folder (or other storage area) which contains (or which willeventually contain) the search data file 225. In at least some exampleembodiments, these access rights prevent at least some otherapplications (apart from the third party application) from accessing thesearch data file 225. In some example embodiments, at 602, the searchapplication 221 is granted read-only privileges to the search data file225. Since the search data file 225 may not yet exist, such read-onlyprivileges may be granted to the search application 221 by granting thesearch application 221 read-only access to the folder (or other storagearea) within which the search data file 225 will be stored. The accessrights to a folder may determine the access rights to the filescontained within that folder. Read-only access means that the searchapplication 221 may read from the search data file 225 but may not writeto the file.

In some example embodiments, at 602, the third party application 226 isgranted read and write privileges for the search data file 225. That is,the third party application 226 is permitted to both read from thesearch data file 225 and to write to the search data file 225. As notedabove, since the search data file 225 may not yet be created when 602 isperformed, these rights may be assigned to the folder (or other storagearea) within which the search data file 225 will be stored.

In some example embodiments, at 602, the operating system may configurethe access rights to the search data file 225 (and/or to the folder orother storage area where it is to be stored) to prohibit otherapplications (apart from the third party application 226 and the searchapplication 221) from reading from the search data file 225 and/orwriting to the search data file 225. In at least some exampleembodiments, all other applications (apart from the third partyapplication 226 and the search application 221) are prohibited fromreading from or writing to the search data file 225. That is, the searchdata file 225 is configured so that it may be used by the searchapplication 221 and the third party application 226 but may not be usedby other applications. This allows the third party application 226 toshare data with the search application without compromising the securityof the data.

The search data file 225 is stored at a location of memory of theelectronic device 201 at which the search application 221 is configuredto scan for a search data file 225. In at least some exampleembodiments, the search data file 225 may be stored at a folder that hasa predetermined relative path. This relative path may be the same for aplurality of third party applications, but the absolute path may differ.That is, all applications that are using a search data file 225 to passdata to the search application 221 may store the data in a location thathas a common relative path. For example, it may be stored at a commonpath relative to the main folder of the third party application whichstores it. For example, each application may have its own main folder orstorage location which may be unique for the application. However, thesearch data file 225 for each application may be stored in a commonlocation relative to that main folder; for example, in asharewith/search sub-folder named search_data or named using anothercommon name.

By using relative paths that are predetermined and that are common for aplurality of applications, the operating system 222, the searchapplication 221 and the third party application 226 may be able tocoordinate in order to allow search data (i.e. the search data file 225)to be shared with the search application 221, but not with otherapplications. More particularly, since the location at which the searchdata file 225 will be stored is predictable to the operating system 222,the operating system 222 may identify the proper location at which thesearch data file 225 is stored (or will be stored) and may use thisinformation to grant access rights (at 602) in the manner discussedabove.

At 604, the third party application 226 may store data in the searchdata file 225. The search data file 225 may be prepared in the formatdescribed above with reference to FIG. 2 and may be stored in thelocation described above (e.g. at a location having a predeterminedrelative path). More particularly, the search data file 225 is preparedaccording to one or more predetermined format rules by the third partyapplication 226. These predetermined format rules are recognized by thesearch application 221 so that the data stored by the third partyapplication may be properly interpreted by the search application.

As noted above, in some example embodiments, the predetermined formatrules allow a record having a plurality of fields to be establishedwithin the search data file. That is, the predetermined format rules mayallow the third party application 226 to create a link between datawhich are related but which may be of different types. As noted in thediscussion of FIG. 2 above, in at least some example embodiments, thepredetermined format rules that are used by the third party application226 (to store data) and the search application 221 (to read data)utilize a table-based structure in order to create relationships betweendata. That is, data may be included in a table within the search datafile 225. The rows (or columns) of the table may be used to establishrecords. For example, where rows are used to establish records, all datain a given row may be associated with a common record and differentcolumns may denote different fields.

As also noted above in the discussion of FIG. 2, the predetermined rulesmay allow the third party application 226 to store both searchable data(i.e. data that will be searched by the search application 221) andnon-searchable data (i.e. data that will not be searched by the searchapplication 221). That is, a first portion of the search data file 225may be searchable, while a second portion of the search data file 225may be configured to be excluded from a search. The second portion ofthe search data file may store metadata regarding the first portion ofthe search data file. The metadata may include rendering and/orlaunching information which will be used by the search application 221when rendering search results and/or when invoking a search result.

The searchable data may be any data that a user may wish to search. Moreparticularly, application data associated with the third partyapplication 226 is included in the searchable data. This applicationdata is data that is associated with a specific application. It may bedata that is generated within or by the third party application 226 orthat is otherwise input to the third party application.

The predetermined format rules that are used by the third partyapplication 226 to store data (and used by the search application 221 toread data) may allow specific metadata to be associated with a specificrecord. That is, an association may be provided between specificmetadata in the second portion of the search data file (i.e. thenon-searchable portion) and specific data in the first portion of thesearch data file (i.e. the searchable portion). For example, a locationof an image that will be displayed when a particular record matches asearch query may be provided. Other example types of metadata aredescribed with reference to FIG. 2.

As noted in the discussion of FIG. 2, the searchable data and thenon-searchable data may be stored in separate tables. For example, insome example embodiments, at 604, searchable data (data that the thirdparty application 226 would like the search application 221 to perform asearch with) is stored in a searchable data table 130 whilenon-searchable data (data that the third party application 226 would notlike the search application 221 to perform a search with) may be storedin a non-searchable data table 132. The non-searchable data table may,in at least some example embodiments, store metadata of the typedescribed above. In at least some example embodiments, data of thesearchable data table 130 may be related with metadata in thenon-searchable data table 132 by row number or by column number.

Thus, at 604, searchable data and, in at least some example embodiments,non-searchable data (such as metadata) may be stored according to thepredetermined rules described above and, in at least some exampleembodiments, in the format described above with reference to FIG. 2.

The search data file 225 may be stored (at 604) in a file that follows anaming convention and/or uses a file extension that is known to thesearch application 221. That is, all third party applications whichgenerate a search data file 225 may utilize a common naming conventionfor the file and/or may use a common extension for the file. As will bedescribed below with reference to 608, such conventions may be usefulfor the search application 221 to identify the search data file 225.

At 606, a search query is received at the search application 221. Thesearch query may be received via a user interface associated with thesearch application 221 and may rely on an input interface associatedwith the electronic device 201 for input of the search query. Forexample, a physical or virtual keyboard may be used to input the searchquery.

As noted above, in some example embodiments, as-you-type search queriesmay be supported. That is, a search query may be considered to have beenreceived after a character for the search query has been input and/orafter there has been a pause following the input of a character. In someexample embodiments, a user may not need activate a search button (or acarriage return) following input of the character(s) in order to performthe search. In other example embodiments, as-you-type searching may notbe supported and the search query may be considered to be received onlyafter a specific instruction is received to initiate the search (e.g.after the user has activated a search button).

After the search query is received, the search application 221 performsone or more searches based on the search query. More particularly, in atleast some example embodiments, at 608, after the search query isreceived, the search application 221 identifies the search data fileassociated with the third party application 226. As noted above, in atleast some example embodiments, the search application 221 may (at 608)locate a folder containing the search data file by utilizing apredetermined relative path that is the same for a plurality of thirdparty applications. More particularly, as noted above, each third partyapplication which stores data in a search data file 225 to passinformation to the search application 221 may store that file using acommon relative path. That is, the relative path used by eachapplication to store the data may be the same, but the absolute path maydiffer for different applications. The search application 221 isconfigured with information identifying the relative path and may, at608, use the relative path information to identify the location at whichthe third party application may store the search data file 225. Thistechnique may be used to identify a plurality of locations where aplurality of third party applications may store their respective searchdata files.

As also noted above, in some example embodiments, the search data file225 may be stored (at 604) in a file that follows a naming conventionand/or uses a file extension that is known to the search application221. This naming convention information and/or file extensioninformation may also be used (at 608) by the search application toidentify the search data file 225 for a third party application 226.

When a search data file 225 is located, the search application 221 maysearch within the search data file 225. More particularly, the searchapplication 221 may search at least a portion of the search data fileusing the search query to identify information that matches the searchquery.

Since the search data file 225 was stored prior to receiving the searchquery (i.e. prior to 606), the search data file 225 may be searched (at609) by the search application 221. More particularly, the third partyapplication 226 need not be invoked in order to perform the search. Ifthe third party application 226 is not already running, it may remain ina state in which it is not running. That is, the search application 221may perform the search using the search data file without requiringassistance from the third party application 226. The third partyapplication may not run during the period of time between when thesearch query is received (at 606) and the period of time when searchresults are subsequently displayed (which will be discussed below withreference to 614), and yet search results may be generated based onapplication data for that third party application.

The search application 221 is configured to use the same predeterminedformat rules that were used to create the search data file 225 whensearching the search data file 225 and interpreting the results of thesearch. For example, as noted above, the predetermined format rules maydefine a searchable portion of the search data file 225 (e.g. asearchable data table 130) and a non-searchable portion of the searchdata file 225 (e.g. a non-searchable data table 132). When performingthe search at 609, the search application 221 performs the search on thesearchable portion of the file, but excludes from the search, thenon-searchable portion of the file.

Thus, at 609, the search application 221 identifies one or more fieldswhose contents match the search query. It will be appreciated that, inat least some example embodiments, for the contents to be considered to“match” the search query, only a portion of the contents of the fieldmay be required to match a search query. By way of example, if a searchquery is “hello” and a field contains data including “hello how are youtoday”, then the contents of the field may be considered to match thesearch query. It will be appreciated that special search characters orcommands may be used in some example embodiments to influence the searchalgorithm (i.e. to influence what may be considered a “match”). Forexample, quotations may be used to search a phrase, binary searchcommands (such as AND, &, OR) may be supported in some exampleembodiments, and wildcard searching (e.g. using a * or other wildcardcharacter) may be supported in some example embodiments. Other specialsearch commands may also be used in some example embodiments.

As noted in the discussion of FIG. 2 above, the predetermined formatrules that are used to create the search data file 225 may allow anassociation between related data to be created. For example, a singlerecord may be associated with multiple fields, each containinginformation of a different type. Similarly, specific searchable data maybe associated with corresponding non-searchable data (such as metadata).

Thus, in at least some example embodiments, at 610 the predeterminedformat rules may be used to identify associated information in thesearch data file. The associated information is information that isrelated to the information that matches the search query (i.e. theinformation identified at 609). The associated information may includeinformation that does not, itself, match the search query, but which isassociated with information that matches the search query. Similarly,the associated information may include information that was not searchedsince it was included in the non-searchable portion of the search datafile 225 (e.g. the non-searchable data table 132), but which is relatedto a record containing information that matched the search query.

For example, in some example embodiments, the information matching thesearch query (i.e. the information identified at 609) is contained in afirst field of a record. In some such example embodiments, at 610, theassociated information may be another field of the same record. That is,at 610 the search application may identify a second field in the recordthat includes the first field. The second field may not, itself,correspond to the search query. However, the second field may be usedwhen the search results are displayed (which will be discussed belowwith reference to 614). More particularly, a display of the searchresults may include both the contents of the first field and thecontents of other fields of the same record, such as the second field.

Similarly, in some example embodiments, the associated information whichis identified at 610 may include metadata provided in the non-searchableportion of the search data file 225 (e.g. the non-searchable data table132). That is, at 610 the search application may retrieve the specificmetadata that is associated with the information in the search data file225 that matches the search query (i.e. the information identified at609). For example, metadata associated with a record containing a fieldthat matched the search query may be identified.

At 612, in at least some example embodiments, the search applicationobtains search results from at least one other source. The at least oneother source may include other third party applications (e.g. byfollowing 608, 609 and 610 to identify and extract data from the searchdata file(s) 225 for the other application(s)). The at least one othersource may, in some example embodiments, include a service 227 (FIG. 1).The searching of service data 228 associated with a service will bedescribed in greater detail below with reference to FIG. 4. The at leastone other source may, in some example embodiments, include a service,application or data stored at a different memory component than thememory component used to store the third party application 226 and/orthe search data file 225 for that third party application 226. Forexample, in some example embodiments, data on a memory module 230(FIG. 1) may be searched. As will be described in greater detail belowwith reference to FIGS. 5 and 6, in some example embodiments, dataassociated with a separate sandbox may be searched.

The at least one other source may also, in at least some exampleembodiments, include application names. That is, the search application221 may also search (at 612), the names of third party applicationsinstalled on the electronic device 201 to determine whether any of thethird party applications have a name that matches the search query.

At 614, the search application 221 generates a display of searchresults. The display is generated based on both the information matchingthe search query (i.e. the information identified at 609) and theassociated information (i.e. identified at 610). For example, as notedabove, where a field of a record includes content that matches thesearch query, then that field may be displayed. However, other fieldsassociated with the same record may also be displayed. In some exampleembodiments, the complete record may be displayed. An example display900 will be discussed below with reference to FIG. 7. In the example ofFIG. 6, a search query of “Hockey” causes a third party application tobe searched. Three records are identified since each of those recordsincludes a field containing the search query. However, other fields,such as a date field, are also displayed.

Other associated information that may be used to generate the displaymay include metadata. The metadata is data that is included in a portionof the search data file 225 that is not searchable. Thus, the termmetadata as used herein refers to the unsearchable portion of the searchdata file 225. The metadata is, in at least some example embodiments,not directly displayed, but it is used to generate the display.

The metadata that is used to generate the display may take differentforms in different example embodiments. By way of example, in someexample embodiments, the metadata may specify an image path. The imagepath may be the path of an icon that is to be displayed when a searchquery matches a field of a particular record. In such cases, at 614, thesearch application 221 may retrieve the image and include the imagealong with its associated search result.

By way of further example, in some example embodiments, an unbounduniform resource identifier (URI) may be specified in the metadata. TheURI may be used to invoke a given search result. That is, the URI may beused to open the search result in the third party application 226. Insuch example embodiments, the display may be generated so that a searchresult may be activated using an input interface (such as a touchscreendisplay) and the activation will cause the URI to be used to invoke thesearch result. In at least some example embodiments, if no URI isprovided by the third party application 226 and a search result isactivated, then the third party application associated with that searchresult may be invoked. An application switch may be used when the thirdparty application 226 is invoked which directs the third partyapplication 226 to open a specific record. For example, a recordidentifier associated with the search result which was activated may beused to inform the third party application 226 of the record that is tobe opened.

By way of further example, in at least some example embodiments, themetadata may be used to group or order search results. For example,metadata may assign records to one of a plurality of different groups.Multiple records may, in some example embodiments, be assigned to acommon group. This group information may be used by the searchapplication 221 to generate the display. For example, in some exampleembodiments, when multiple records of a common group include contentthat corresponds to the search query, those records may be displayedtogether in a common group. Alternatively, in some example embodiments,when multiple records of a common group include content that correspondsto the search query, only a single one of those records may bedisplayed.

Similarly, metadata may establish the relative priority of records. Whenthe search application 221 displays search results which identify aplurality of records associated with a single third party application226, the search results may be displayed in an order that is determinedby the metadata specifying the relative priorities.

Since the search application 221 provides searching, more than one datasource is searched (as was explained with reference to 609 and 612) andthus the display may include the search results associated with morethan one data source. More particularly, as noted above, the display mayinclude the search results obtained (at 609) from the search data file225 and may also include the search results that were obtained from theother source(s) at 612.

Searching of Data Associated with a Service

Referring now to FIG. 4, a flowchart of a further example method 700 forproviding searching of data will now be discussed. The example method700 may be performed by the electronic device 201 of FIG. 1 (or theelectronic device 201 of FIG. 5). More particularly, the processor 240of the electronic device 201 may be configured to perform the method700. A memory associated with the processor 240 may includeprocessor-executable instructions which, when executed, cause theprocessor 240 to perform the method 700 of FIG. 4. In at least someexample embodiments, these processor-executable instructions areprovided in one or more of the software modules described above withreference to FIG. 1. For example, a service 227, a search application221 and/or an operating system 222 associated with the electronic device201 may configure the electronic device 201 to perform the method 700.Since a plurality of different software components may cause the method700 to be performed, the method 700 may be comprised of a plurality ofsub-methods each performed by a different software component.

For example, a portion 750 of the method 700 may be performed by theservice 227. That is, the service 227 may be configured to cause theprocessor 240 to perform a portion 750 of the method 700. This portion750 may also be considered a method.

Similarly, a portion 752 of the method 700 may be performed by thesearch application 221. That is, the search application 221 may beconfigured to cause the processor 240 to perform a portion 752 of themethod 700. This portion 752 may also be considered a method.

Thus, FIG. 4 describes a plurality of methods that may be performed. Amethod is described that may be provided by a service 227 (i.e. theportion 750 of the method 700), and a method is described that may beprovided by a search application 221 (i.e. the portion 752 of themethod). Additionally, a method 700 may be jointly performed by thesearch application 221 and the service 227, or by other softwareapplications or modules.

As noted in the discussion of FIG. 1 above, a service differs from anapplication in that the service 227 is generally configured to run as abackground process on the electronic device 201. More particularly,applications typically require some user input (such as selecting anicon associated with the application from a home or start page) in orderto cause them to run on the electronic device 201. When the applicationstarts up, it is typically accompanied by an associated graphical userinterface and the graphical user interface may remain active while theapplication runs. In contrast, a service 227 may run without a graphicaluser interface and/or may not require user input in order to run. Theservice 227 may be automatically initiated; for example, when theelectronic device 201 first boots up.

Thus, at 702 the service 227 is run as a background process on theelectronic device. This may be performed automatically when theelectronic device 201 is powered on and/or awakened from a locked orsleep state. Since the service 227 is ordinarily running (e.g. as abackground process), services may provide search result data to a searchapplication 221 in a manner that differs from the manner by which athird party application provides search results. As noted in thediscussion of FIG. 3, applications may specially prepare search databefore a search query is received by a search application 221 and thesearch application 221 may perform the search of this data. In contrast,in some example embodiments, a service 227 may perform the searching ofits service data 228 after a search query is received.

More particularly, in the method 700 of FIG. 4, the search query isreceived at the search application at 606. This feature is described ingreater detail with reference to FIG. 3. The search query is receivedwhile the service 227 is running as a background process on theelectronic device 201. In response to receiving the search query, thesearch application provides (at 704) the search query to the service227. That is, the search query is, at 704, passed to the service 227 toallow the service 227 to perform a search based on the search query.

The service 227 performs the search based on the search query (at 706)and provides the results to the search application. These results arereceived at 708 at the search application. Thus, in response to passingthe search query to the service, search results are received from theservice. These search results are formatted according to predeterminedrules which allow the search application 221 to understand the nature ofthe search results being provided. For example, the search results maybe provided using one or more of the predetermined rules described abovewith reference to the search data file 225 of FIG. 2. That is, the samerules that are used to format the search data file 225 may be used bythe service 227 to format the search results that it provides to thesearch application 221.

For example, any of the metadata described above with reference to FIG.2 may be included with the search results that are provided by theservice 227 at 752. Accordingly, each search result that is provided bythe service 227 to the search application 221 may be associated withspecific metadata which may be used by the search application whenrendering search results. For example, metadata may specify an imagepath (of an image that is to be displayed with a search result), a URIfor invoking a particular search result, ordering data which may be usedby the search application to determine the relative ordering of thesearch results when they are displayed, and/or grouping informationwhich may be used to group search results. Other types of metadata maybe included in at least some example embodiments.

After the search results are received at the search application (at708), they are displayed by the search application at 710. While thesearch application performs the rendering of the search results, theservice 227 may be permitted to influence or control the manner by whichthe search results are displayed. For example, as noted above, metadatathat is included with the search results may be used for this purpose.

It will be appreciated that the display generated at 710 may include thefeatures of the display generated at 614 of the method 600 of FIG. 3.For example, prior to the display (at 710), the method 700 may include astep of obtaining search results from other sources. Example methods bywhich search results may be obtained from other sources are described ingreater detail above; for example, with reference to 612 of FIG. 3. Insuch example embodiments, the display generated at 614 may include boththe search results from the service 227 and the search results from theat least one other source.

Furthermore, the features 704, 706, 708 of the method 700 of FIG. 4 maybe performed, in some example embodiments, together with the features ofthe method 600 of FIG. 3 which allow for a search data file 225associated with a third party application 226 to be searched. Forexample, the features 704, 706, 708 of the method 700 of FIG. 4 may beperformed when obtaining other search results from other sources at 612of the method 600 of FIG. 3.

Further Example Electronic Device

Referring now to FIG. 5, a block diagram of a further example electronicdevice 201 is illustrated. The electronic device 201 of FIG. 5 mayinclude many features of the electronic device 201 of FIG. 1, and thedescription of these features will not be repeated but like referencenumerals have been used to denote like components.

The example electronic device of FIG. 5 utilizes a sandboxing techniquewhich allows for the separation of data and/or applications into two ormore separate operating environments.

In the electronic device 201 of FIG. 5, at least some files andapplications that access the files can be classified according to asandbox 250, 252. A sandbox (also referred to herein as a workspace) canbe defined as a workspace, perimeter or environment, in which the filesand/or applications are restricted. The workspace can be one of aplurality of partitions. Each workspace is separate from each of theother workspaces such that a tightly-controlled set of resources forcontrolling entities such as, but not limited to, data files, networkconnections and hardware and running applications that access theentities provides a security mechanism for separating the launching andrunning of programs and entities in the different workspaces. Rule setscan be implemented to provide full control over what processes arestarted, spawned (by other applications), allowed to access entitiessuch as, but not limited to, data files, network connections, andhardware, or allowed to inject code into other applications. Sandboxingprovides a security system where data is prevented from movement betweenthe different areas. More specifically, sandboxes 250, 252 (and othercomponents, and software on the electronic device 201) may be configuredsuch that data is prevented from being moved between different sandboxes250, 252.

The sandboxes 250, 252 generally allow the electronic device 201 to beused in different operational contexts while maintaining file security.For example, the electronic device 201 may be used for both personal useand also for business use in some example embodiments. Business filesand applications be kept separately from personal files and application(e.g. business files may be kept in a corporate sandbox and personalfiles may be kept in a personal sandbox and the sandboxes may be walledoff from one another so that file transfers between the sandboxes areprevented or controlled). Thus, the sandboxes 250, 252 may be consideredto be secure and lockable file systems, in at least some exampleembodiments.

Accordingly, in at least some example embodiments, there can be multiplemodes or workspaces provided by the electronic device 201. Anapplication running in one sandbox 250, 252 can access entities such as,but not limited to, data files, network connections, and hardware in thesandbox 250, 252 in which it is running, but can be restricted fromaccessing and operating on entities such as, but not limited to, datafiles, network connections, and hardware in another sandbox.

For example, the system may be partitioned into two workspaces (assecure workspaces, i.e., sandboxes) such as a corporate sandbox and apersonal sandbox. The data and files in the corporate sandbox can bestrictly separated from applications or programs running the personalsandbox. This secure separation provides a security mechanism thatallows a system to operate in the numerous modes. The establishment of asecure separation to provide a security mechanism that allows a systemto operate in numerous modes is not limited to two sandboxes and can beimplemented for three or more sandboxes.

In FIG. 5, the memory is illustrated as being partitioned into aplurality of sandboxes 250, 252. In the example embodiment illustrated,the memory is partitioned into a first sandbox 250 and a second sandbox252. Each sandbox 250, 252 may be associated with separate data and/orapplications. For example, in the example illustrated, the first sandbox250 is associated with a first third party application 226 a, which maybe associated with a first search data file 225 a (which may be of thetype described with reference to FIG. 2) and the second sandbox 252 isassociated with a second third party application 226 b, which may beassociated with a second search data file 225 b (which may also be ofthe type described with reference to FIG. 2).

Similarly, in some example embodiments, one or more services may beprovided within a sandbox. For example, a first service 227 a associatedwith first service data 228 a may be provided in a first sandbox 250 anda second service 227 b associated with second service data 228 b may beprovided in the second sandbox 252.

In at least some example embodiments, one or more highly trustedapplications (or services) may act as hybrid applications (or services).A hybrid application is a trusted application that is capable of andpermitted to concurrently access files from more than one sandbox 250,252. That is, the hybrid application is permitted to access data from aplurality of sandboxes 250, 252 within a single instance of the hybridapplication. The ability to access files from a plurality of sandboxes250, 252 at the same time may be provided to the hybrid application byhigher-level system components, such as a sandbox management applicationor module (not shown) which manages the sandboxes 250, 252 andadministers a set of access rules for the sandboxes. The sandboxmanagement application or module may, for example, be provided by theoperating system 222.

In at least some example embodiments, the search application 221 is ahybrid application. That is, the search application is configured toaccess data within the first sandbox 250 and also data within the secondsandbox 252. For example, the hybrid search application is configured toaccess a first search data file 225 a from a first sandbox 250 and toalso access a second search data file 225 b from a second sandbox 252.

In at least some example embodiments, one or more of the sandboxes maybe lockable (e.g. the first sandbox 250 may be a work/corporate sandboxwhich is lockable). That is, one or more of the sandboxes may be lockedso that applications and data associated with that sandbox are notaccessible until the sandbox is unlocked. Such locking may provide anadditional level of security to the electronic device 201. For example,an electronic device 201 having corporate data stored within a corporatesandbox may be used by someone who is not authorized to view or accessthe corporate data. More particularly, the corporate sandbox could belocked and the unauthorized person may be permitted to utilize theelectronic device 201 while only a personal sandbox is unlocked andavailable.

Search with Sandboxing

Referring now to FIG. 6, an example method 800 is illustrated. Themethod 800 may be used to provide searching in an environment in whichsandboxes of the type described with reference to FIG. 5 are used.

The example method 800 may be performed by the electronic device 201 ofFIG. 5. More particularly, the processor 240 of the electronic device201 may be configured to perform the method 800. More particularly, amemory associated with the processor 240 may includeprocessor-executable instructions which, when executed, cause theprocessor 240 to perform the method 800 of FIG. 6. In at least someexample embodiments, these processor-executable instructions areprovided in one or more of the software modules described above withreference to FIG. 1 (and also illustrated in the electronic device 201of FIG. 5). For example, in at least some example embodiments, thesearch application 221 may include instructions which configure theprocessor to perform the method 800 of FIG. 6.

At 806, a search query is received at the search application 221. Thesearch query may be received in the manner described above withreference to 606 of FIG. 3. The search application is a hybridapplication that is configured to access data within a first sandbox anddata within a second sandbox. The first sandbox 250 is lockable.

In response to receiving the search query, the search application may(at 807), determine whether the first sandbox 250 is locked.

If the sandbox is locked, then search results associated with the firstsandbox are not obtained. For example, in example embodiments in whichdata associated with a third party application is being searched in themanner described with reference to FIG. 3, then the search is notperformed on a first search data file 225 a (FIG. 5) which is associatedwith a first third party application 226 a that is associated with thefirst sandbox 250. Similarly, the search may not be performed on servicedata 228 a associated with a service 227 a on the first sandbox 250.That is, either a search query is not passed to the service 227 a (inthe manner described with reference to 704 of FIG. 4), or the searchquery may be passed but the service 227 a does not return search resultssince it determines that it is associated with a locked sandbox.

Instead, the method 800 may proceed to 812 where search results fromanother source are obtained (for example, applications or servicesassociated with the second sandbox may be searched, assuming the secondsandbox is not in a locked state or is not lockable).

If, however, it is determined that the first sandbox is not locked, thenthe method may proceed to 808 where search results associated with thefirst sandbox are obtained. For example, if the first sandbox isunlocked, search results may be obtained from one or more applicationsassociated with the first sandbox 250. For example, the steps 608, 609,and/or 610 of the method 600 of FIG. 3 may be used to identify a firstsearch data file 225 a for a third party application 226 a associatedwith the first sandbox 250 and to extract search results associated withthe search query from the identified file.

Irrespective of whether the first sandbox is locked, search results fromthe second sandbox 252 may be obtained (at 812) (unless, for example,the second sandbox is locked). For example, search results may beobtained from a second search data file 225 b prepared by a second thirdparty application 226 b associated with the second sandbox 252.

At 814, the search results are displayed. For example, if the firstsandbox was not locked and search results were obtained from both thefirst sandbox and the second sandbox, search results from the firstsandbox may be displayed together with search results from the secondsandbox. For example, search results that were obtained fromapplications (such as the first third party application 226 a)associated with the first sandbox 250 are displayed together with searchresults for applications (such as the second third party application 226b) associated with the second sandbox 252.

The display provided at 814 may include features described above withreference to the display features of the method 600 of FIG. 3 (which aredescribed with reference to 614) and/or the display features of themethod 700 of FIG. 4 (which are described with reference to 710).Furthermore, the display may include the features described below withreference to the example display 900 of FIG. 7.

In some example embodiments, the display generated at 814 may includeone or more indicators to distinguish search results associated with thefirst sandbox 250 from search results associated with the second sandbox252. For example, a briefcase icon or an icon of another type may bedisplayed adjacent to search results associated with a first sandbox 250(which may be a corporate sandbox) and another icon or no icon may bedisplayed adjacent to search results associated with the second sandbox252.

In some example embodiments, an application associated with the firstsandbox 250 may have an equivalent application operating within thesecond sandbox 252. For example, in some example embodiments, eachsandbox 250, 252 may have its own web browser. Each of theseapplications may have their own data. For example, a first third partyapplication 226 a and a second third party application 226 b may beequivalents (i.e. the same application operating in differentsandboxes), but the first third party application 226 a associated withthe first sandbox 250 and the second search data file 225 b haveseparate search data files 225 a, 225 b. Thus separate search resultsmay be generated for each of these applications. However, in at leastsome example embodiments, the search application is configured toidentify such equivalent applications and to merge the search resultsfrom equivalent applications (that may be associated with separatesandboxes) when generating a display. For example, using the web browserexample noted above, a single web browser set of search results 902(FIG. 7) may be displayed which lists the results from both web browserstogether but the display may include one or more indicators 905 (FIG. 7)to identify the source of the data (i.e. whether the search results isassociated with the first sandbox 250 or the second sandbox 252).

Example Display

An example display 900 will now be described with reference to FIG. 7.The example display 900 (or a variant thereof) may be generated and/ordisplayed during any one or more of the “display search results” step(s)614, 710, 814 of FIGS. 3, 4 and 6.

The display 900 may include a search input field 906, which is a textinput field in which a search query may be input. In the example, thesearch query is “Hockey.”

The display 900 may include search results associated with a pluralityof applications, services, and/or files. For example, the display 900includes application name search results 904. The application namesearch results 904 section lists applications associated with theelectronic device 201 having a name that matches the search query. Theseapplications may, in some example embodiments be associated with aplurality of sandboxes 250, 252. In some such example embodiments, anindicator 905 may be used to indicate the sandbox which is associatedwith the application.

In the example, web browser search results 902 are included. The webbrowser search results 902 illustrate an example of how search resultsmay be displayed when equivalent applications are provided on thedevice. More particularly, equivalent applications may be providedwithin multiple sandboxes (e.g. a web browser may be provided on both afirst sandbox and a second sandbox). As noted in the discussion of FIG.6 above, in such example embodiments, the search application may mergethe search results from these equivalent applications, but may includean indicator 905 of the source of a search result.

It will be appreciated that similar techniques may be used todistinguish between search results associated with different memorycomponents. For example, search results for data stored on a removablememory module may be merged with search results from data store oninternal memory. In some such example embodiments, an indicator may beused to identify whether a particular search result is associated withremovable memory or internal memory.

The display 900 includes a service search results 910 section. Theservice search results 910 section displays search results associatedwith a service 227. In the example, the service is an email service andthe search results are emails. These search results may, in at leastsome example embodiments, be obtained in the manner described above withreference to FIG. 4.

The display 900 further includes a third party application searchresults 912 section. This section provides search results that areassociated with a third party application. These search results may, inat least some example embodiments, be obtained in the manner describedabove with reference to FIG. 3.

As noted in the discussion of FIG. 3 above, the third party applicationsearch results 912 section may include information from a field whichmatches the search and may also include information from other relatedfields. For example, a date field is included even though the date doesnot correspond with the search query.

Metadata may be used to group and/or order the search results in thethird party application search results 912 section. For example, in theexample illustrated metadata may specify that the hockey games thatalready have enough players (i.e. are “filled”) are to be groupedtogether. This grouping, established by the third party applicationassociated with the search results overrides other default ordering thatmight appear to be otherwise natural. For example, the grouping providedin the metadata may take precedence over alphabetical or chronologicalordering.

While the present application is primarily described in terms ofmethods, a person of ordinary skill in the art will understand that thepresent application is also directed to various apparatus such as anelectronic device 201 including a mobile communications device. Theelectronic device 201 includes components for performing at least someof the aspects and features of the described methods, which may be byway of hardware components (such as the memory 244 and/or the processor240), software or any combination of the two, or in any other manner.Moreover, an article of manufacture for use with the apparatus, such asa pre-recorded storage device or other similar computer readable storagemedium including program instructions recorded thereon, or a computerdata signal carrying computer readable program instructions may directan apparatus to facilitate the practice of the described methods. Forexample, a compute readable storage medium may include computerexecutable instructions for performing one or more of the methodsdescribed herein. It is understood that such apparatus and articles ofmanufacture also come within the scope of the present application.

The term “computer readable medium” or “computer readable storagemedium” as used herein means any medium which can store instructions foruse by or execution by a computer or other computing device includingbut not limited to, a portable computer diskette, a hard disk drive(HDD), a random access memory (RAM), a read-only memory (ROM), anerasable programmable-read-only memory (EPROM) or flash memory, anoptical disc such as a Compact Disc (CD), Digital Versatile Disc (DVD)or Blu-ray™ Disc, and a solid state storage device (e.g., NAND flash orsynchronous dynamic RAM (SDRAM)).

Example embodiments of the present application are not limited to anyparticular operating system, system architecture, mobile devicearchitecture, server architecture, or computer programming language.

The various example embodiments presented above are merely examples.Variations of the innovations described herein will be apparent topersons of ordinary skill in the art, such variations being within theintended scope of the present application. In particular, features fromone or more of the above-described example embodiments may be selectedto create alternative example embodiments including a sub-combination offeatures which may not be explicitly described above. In addition,features from one or more of the above-described example embodiments maybe selected and combined to create alternative example embodimentsincluding a combination of features which may not be explicitlydescribed above. Features suitable for such combinations andsub-combinations would be readily apparent to persons skilled in the artupon review of the present application as a whole. The subject matterdescribed herein and in the recited claims intends to cover and embraceall suitable changes in technology.

The invention claimed is:
 1. A processor-implemented method of searchingdata associated with an electronic device, the method comprising:receiving a search query adapted for matching against fields of records;obtaining first search results associated with the search query from afirst source, the first search results corresponding to recordsassociated with the first source having one or more fields matching thesearch query; determining that a first lockable sandbox is unlocked andobtaining second search results associated with the first lockablesandbox and the search query, the second search results corresponding torecords associated with the first lockable sandbox having one or morefields matching the search query; and presenting the second searchresults and the first search results.
 2. The method of claim 1, whereinthe first source is a second sandbox.
 3. The method of claim 2, whereinthe first lockable sandbox is a corporate workspace and the secondsandbox is a personal workspace.
 4. The method of claim 2, wherein thefirst lockable sandbox is configured to prevent data from being moved tothe second sandbox.
 5. The method of claim 2, wherein the search queryis received within a hybrid search application which is configured toaccess both the first lockable sandbox and the second sandbox.
 6. Themethod of claim 2, wherein presenting the first and second searchresults comprises: identifying an application associated with the firstlockable sandbox having an equivalent application associated with thesecond sandbox; and merging the search results from the equivalentapplications.
 7. The method of claim 1, wherein presenting comprises:displaying an indicator in association with at least one of the secondsearch results, the indicator identifying the source of the searchresult as the first lockable sandbox.
 8. The method of claim 1, whereinobtaining the second search results comprises obtaining search resultsfrom an application associated with the first lockable sandbox.
 9. Anelectronic device comprising: a memory; a processor in communicationwith the memory, and configured to: receive a search query adapted formatching against fields of records; obtain first search resultsassociated with the search query from a first source, the first searchresults corresponding to records associated with the first source havingone or more fields matching the search query; determine whether a firstlockable sandbox is unlocked; and when the first lockable sandbox isunlocked: obtain second search results associated with the firstlockable sandbox and the search query, the second search resultscorresponding to records associated with the first lockable sandboxhaving one or more fields matching the search query; and present thesecond search results and the first search results.
 10. The electronicdevice of claim 9, wherein the first source is a second sandbox.
 11. Theelectronic device of claim 10, wherein the first lockable sandbox is acorporate workspace and the second sandbox is a personal workspace. 12.The electronic device of claim 10, wherein the first lockable sandbox isconfigured to prevent data from being moved to the second sandbox. 13.The electronic device of claim 10, wherein the search query is receivedwithin a hybrid search application which is configured to access boththe first lockable sandbox and the second sandbox.
 14. The electronicdevice of claim 10, wherein presenting the first and second searchresults comprises: identifying an application associated with the firstlockable sandbox having an equivalent application associated with thesecond sandbox; and merging the search results from the equivalentapplications.
 15. The electronic device of claim 10, wherein presentingcomprises: displaying an indicator in association with at least one ofthe second search results, the indicator identifying the source of thesearch result as the first lockable sandbox.
 16. The electronic deviceof claim 10, wherein obtaining the second search results comprisesobtaining search results from an application associated with the firstlockable sandbox.
 17. The electronic device of claim 10, wherein theprocessor is further configured to: when the first lockable sandbox islocked, present the first search results and not the second searchresults.
 18. A non-transitory computer readable storage mediumcomprising computer-executable instructions which, when executed,configure a processor to: receive a search query adapted for matchingagainst fields of records; obtain first search results associated withthe search query from a first source, the first search resultscorresponding to records associated with the first source having one ormore fields matching the search query; determine whether a firstlockable sandbox is unlocked; and when the first lockable sandbox isunlocked: obtain second search results associated with the firstlockable sandbox and the search query, the second search resultscorresponding to records associated with the first lockable sandboxhaving one or more fields matching the search query; and present thesecond search results and the first search results.
 19. The computerreadable storage medium of claim 18, wherein the first source is asecond sandbox.
 20. The computer readable storage medium of claim 19,wherein the first lockable sandbox is a corporate workspace and thesecond sandbox is a personal workspace.